Crystallization of agility: Back to basics

There are a number of agile and traditional methodologies for software development. Agilists provide agile principles and agile values to characterize the agile methods but there is no clear and inclusive definition of agile methods; subsequently it is not feasible to draw a clear distinction between traditional and agile software development methods in practice. The purpose of this paper is to explain the concept of agility in detail; and then to suggest a definition of agile methods that would help in the ranking or differentiation of agile methods from other available methods

The rationale of powertype-based metamodelling to underpin software development methodologies

Metamodelling provides a way of modelling the rules underpinning not only modelling languages such as UML but also processes. In the context of object-oriented development, we evaluate the conceptual framework used to reason about metamodelling from the different perspectives of methodologist, method engineer and software developer. We propose the use of clabjets and powertype patterns as a solution to avoid the present inconsistencies in the use of a strict metamodelling multi-level hierarchy and demonstrate their efficacy in providing a solid and improved framework for OO-based process (and product) metamodelling. Copyright © 2005, Australian Computer Society, Inc

A foundation for multi-level modelling

Multi-level modelling allows types and instances to be mixed in the same model, however there are several proposals for how meta- models can support this. This paper proposes a meta-circular basis for meta-modelling and shows how it supports two leading approaches to multi-level modelling

Supporting Tropos concepts in Agent OPEN

The growth of interest in agent-orientation as a new paradigm has introduced the need for developing concepts, tools and techniques for modeling and engineering agent-based software systems. Object technology has been supporting the development of information systems for many years but is now slowly evolving to encompass more recent ideas relating to the concept of "agent". Integrating agent concepts into existing OO methodologies has resulted in several agent-oriented methodologies, one of which is Agent OPEN. In this paper, we evaluate the existing Agent OPEN description against ideas formulated within Tropos, an agent-oriented software development methodology. © Springer-Verlag Berlin Heidelberg 2004

Using a situational method engineering approach to identify reusable method fragments from the secure TROPOS methodology

Situational method engineering (SME) has as a focus a repository of method fragments, gleaned from extant methodologies and best practice. Using one such example, the OPF (OPEN Process Framework) repository, we identify deficiencies in the current SME support for securityrelated issues in the context of agent-oriented software engineering. Specifically, theoretical proposals for the development of reusable security-related method fragments from the agent-oriented methodology Secure Tropos are discussed. Since the OPF repository has already been enhanced by fragments from Tropos and other non-security-focussed agent-oriented software development methodologies, the only method fragments from Secure Tropos not already contained in this repository are those that are specifically security-related. These are identified, clearly defined and recommended for inclusion in the current OPF repository of method fragments. ©JOT 2010

Incorporating the elements of the mase methodology into agent open

Enterprise-wide, web-based systems can be assisted in their construction by the use of agents and an agent-oriented methodology. As part of an extensive research programme to create such an AO methodology by combining the benefits of method engineering and existing object-oriented frameworks (notably the OPF), we have analysed here contributions to the OPF repository of process components from the MASE agent-oriented methodology, identifying three new Tasks, one additional Technique and two new Work Products

Towards an interoperable metamodel suite: size assessment as one input

In recent years, many metamodels have been introduced in the software engi- neering literature and standards. These metamodels vary in their focus across, for example, process, product, organizational and measurement aspects of software development and have typically been developed independently of each other with shared concepts being only accidental. There is thus an increasing concern in the standards communities that possible conicts of structure and semantics between these various metamodels will hinder their widespread adoption. The complexity of these metamodels has also increased significantly and is another barrier in their appreciation. This complexity is compounded when more than one metamodel is used in the lifecycle of a software project. Therefore there is a need to have interoperable metamodels. As a first step towards engendering interoperability and/or possible mergers between metamodels, we examine the size and complexity of various meta- models. To do this, we have used the Rossi and Brinkkemper metrics-based approach to evaluate the size and complexity of several standard metamodels including UML 2.3, BPMN 2.0, ODM, SMM and OSM. The size and complexity of these metamodels is also compared with the previous version of UML, BPMN and Activity diagrams. The comparatively large sizes of BPMN 2.0 and UML 2.3 suggest that future integration with these metamodels might be more difficult than with the other metamodels under study (especially ODM, SSM and OSM)